@sebastian-roth Can go ahead and mark this as solved. Thank you for the help.

Hi once again!

Our problem, as it stands today, is solved. We ended up trying to install the FOG server on the same subnet with the host machines, which worked. After that we tried putting the machine back on the subnet where all our VMs are located. That broke it. Later the network admin realized that during his configuration he accidentally left a space after the IP on option 66. After that was fixed things stated working out.

So in the end what I was chasing was a typo.

A big thanks to @george1421 for being as helpful as You could during the troubleshooting process.

I am now happily deploying my Windows 10 images. 🙂

@jjsplitter Since you still had firewalld enabled, did you remember to set selinux to permissive? If not you will have a sad time when you try to capture an image.

Well after fighting with this thing for the better part of a week, I think I’ve finally got it stabilized. I’m on revision 3526, and I ended up creating a new image from scratch. Uploading and downloading finally work correctly, and while I do have an issue with the image, that’s a Windows issue not a FOG issue. Thanks to @Wayne-Workman for all his help, hopefully now you guys can move on to more important things, like a stable release. 😄